fix: make zap log messages for agent stdout static - #655
Merged
Conversation
Anton-Kalpakchiev
approved these changes
Aug 10, 2026
thijmv
force-pushed
the
thijmv/agent-static-logs
branch
from
August 11, 2026 14:34
b90cd1a to
6c0b226
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently, some of the logs emitted by the agent use a dynamic message, meaning they cannot be grouped when queried. This PR changes those log messages to be static, injecting the relevant information into additional fields. The addressed logs were identified by inspecting production logs.